Triple
T24622956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buckley (disambiguation) |
E609461
|
entity |
| Predicate | describesTerm |
P24083
|
FINISHED |
| Object | Buckley |
—
|
NE NERFINISHED |
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: Buckley | Statement: [Buckley (disambiguation), describesTerm, Buckley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesTerm Context triple: [Buckley (disambiguation), describesTerm, Buckley]
-
A.
classificationTerm
Indicates that one entity serves as a categorical label or type used to classify or group another entity.
-
B.
componentTerm
Indicates that one term functions as a component or constituent part of another term within a larger conceptual or structural whole.
-
C.
languageTerm
chosen
Indicates that one entity is a linguistic expression (word, phrase, or term) used to denote or label the other entity.
-
D.
keyTerm
Indicates that a term functions as a primary or central concept within a given context or information structure.
-
E.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.