Triple
T29899915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Architect |
E759381
|
entity |
| Predicate | hasEditionLevel |
P171569
|
FINISHED |
| Object | most advanced |
—
|
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: most advanced | Statement: [Architect, hasEditionLevel, most advanced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEditionLevel Context triple: [Architect, hasEditionLevel, most advanced]
-
A.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
B.
hasEditionStatus
chosen
Indicates the specific publication or release status assigned to an edition of a work.
-
C.
hasEditionType
Indicates that one entity is a specific edition type or format classification of another entity (such as a work, publication, or product).
-
D.
hasEditionFeature
Indicates that one edition of a work includes a specific feature, characteristic, or component that distinguishes it from other editions.
-
E.
hasEditionAvailability
Indicates that a particular edition of an item is available in a specified form, location, or channel.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 6:06 p.m.