Triple
T4072369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knight |
E86675
|
entity |
| Predicate | evolvedMeaning |
P53332
|
FINISHED |
| Object | mounted warrior of noble rank |
—
|
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: mounted warrior of noble rank | Statement: [Knight, evolvedMeaning, mounted warrior of noble rank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evolvedMeaning Context triple: [Knight, evolvedMeaning, mounted warrior of noble rank]
-
A.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
B.
evolves
Indicates that one entity undergoes a process of gradual change or development into another, typically more advanced or different, state or form.
-
C.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
-
D.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
-
E.
letterMeaning
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc20ed788190bd935082a348a05d |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa5c52648190b001027f4dba75cb |
completed | March 9, 2026, 4:50 p.m. |
Created at: March 9, 2026, 3:38 p.m.