Triple
T23831733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Rock |
E589529
|
entity |
| Predicate | namingConventionContext |
P153781
|
FINISHED |
| Object | named after a city |
—
|
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: named after a city | Statement: [Little Rock, namingConventionContext, named after a city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingConventionContext Context triple: [Little Rock, namingConventionContext, named after a city]
-
A.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
B.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
C.
codenameContext
Indicates that an entity is associated with or used as a codename within a particular contextual scope or situation.
-
D.
contextName
Indicates the specific contextual label or identifier under which an entity, event, or relation is defined or interpreted.
-
E.
namingFunction
Indicates a relationship where one entity serves as the name or naming mechanism assigned to another entity.
- F. None of above. chosen
Provenance (4 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f6f25c8190bd8957fe3cbefc03 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 8:05 p.m.