Triple
T9298307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicolae |
E223694
|
entity |
| Predicate | usedAcrossGenerations |
P82302
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nicolae, usedAcrossGenerations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAcrossGenerations Context triple: [Nicolae, usedAcrossGenerations, yes]
-
A.
usedAcross
Indicates that something is utilized or applied in multiple different contexts, locations, or domains.
-
B.
usedByGens
chosen
Indicates that something is utilized or employed by one or more generations (or generational groups).
-
C.
hasGenerations
Indicates a relationship where an entity is associated with one or more successive generational levels or cohorts derived from it.
-
D.
followsGenerationsOf
Indicates that one entity comes after and is separated from another by multiple generations in a lineage or succession.
-
E.
usedCross
Indicates that one entity made use of a cross-shaped object or structure, or traversed by means of a crossing point such as a crosswalk or intersection.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08cf50cc8190a025f478dff4f9fd |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.