Triple
T34574617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Period V |
E887716
|
entity |
| Predicate | hasTypicalArtifact |
P114238
|
FINISHED |
| Object | bronze swords |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: bronze swords | Statement: [Period V, hasTypicalArtifact, bronze swords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalArtifact Context triple: [Period V, hasTypicalArtifact, bronze swords]
-
A.
hasSignificantArtifact
Indicates that an entity possesses or is associated with an artifact that is of notable importance, influence, or relevance within a given context.
-
B.
hasCharacteristicArtifact
chosen
Indicates that an entity is associated with a specific artifact that characterizes, exemplifies, or is typical of it.
-
C.
hasTypeOfArtifact
Indicates that one entity is classified as, or belongs to, a particular type or category of artifact in relation to another entity.
-
D.
hasIconicArtifact
Indicates that an entity possesses or is associated with a distinctive, emblematic artifact that represents its identity, history, or significance.
-
E.
hasArtFeature
Indicates that an entity possesses or is characterized by a particular artistic attribute, element, or stylistic feature.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 1, 2026, 2:03 a.m.