Triple
T29269410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | André Danjon |
E742068
|
entity |
| Predicate | hasScaleNamedAfter |
P120681
|
FINISHED |
| Object | Danjon scale |
—
|
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: Danjon scale | Statement: [André Danjon, hasScaleNamedAfter, Danjon scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScaleNamedAfter Context triple: [André Danjon, hasScaleNamedAfter, Danjon scale]
-
A.
hasMeasurementNamedAfter
chosen
Indicates that a measurement unit or scale is named in honor of a particular entity.
-
B.
hasSymbolNamedAfter
Indicates that one entity has a symbol whose name is derived from or dedicated to another entity.
-
C.
hasCollectionNamedAfter
Indicates that an entity has a collection (e.g., of works, items, or artifacts) that is named in honor of or after another entity.
-
D.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
E.
hasPartiallyNamedAfter
Indicates that one entity is partially named in reference to another entity, such that only a portion of its name derives from or honors the other.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 12:47 p.m.