Triple
T38696243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. |
E950005
|
entity |
| Predicate | followsNameFormat |
P35006
|
FINISHED |
| Object | Dr. + Given Name + Surname |
—
|
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: Dr. + Given Name + Surname | Statement: [Dr., followsNameFormat, Dr. + Given Name + Surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsNameFormat Context triple: [Dr., followsNameFormat, Dr. + Given Name + Surname]
-
A.
followsNameOf
Indicates that one entity’s name comes immediately after another entity’s name in a specified ordering or sequence.
-
B.
followsInName
Indicates that one entity’s name is derived from, modeled after, or intentionally patterned to follow the naming of another entity.
-
C.
isNamedAccordingTo
Indicates that one entity receives its name based on, or in accordance with, another entity, rule, or naming convention.
-
D.
usesNicknameInFormat
Indicates that one entity refers to another using a nickname that follows a specific pattern or formatting convention.
-
E.
meetsFormat
chosen
Indicates that something conforms to, satisfies, or is compliant with a specified format or structural standard.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
Created at: May 3, 2026, 4:33 p.m.