Triple
T5392358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curteis |
E120361
|
entity |
| Predicate | hasCharacteristicMeaning |
P3918
|
FINISHED |
| Object | courteous person |
—
|
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: courteous person | Statement: [Curteis, hasCharacteristicMeaning, courteous person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacteristicMeaning Context triple: [Curteis, hasCharacteristicMeaning, courteous person]
-
A.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
B.
describesCharacteristicOf
Indicates that one entity expresses or specifies a characteristic, feature, or property of another entity.
-
C.
methodCharacteristic
Indicates that a particular method or procedure possesses a specified property, feature, or quality.
-
D.
eraCharacteristic
Indicates that a particular quality, feature, or attribute is characteristic of, or typically associated with, a given historical or temporal era.
-
E.
hasLiteralMeaning
chosen
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd8719ff04819089e3a90f90b5e3fc |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.