Triple
T32114344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Incanus |
E820196
|
entity |
| Predicate | hasDebatedEtymology |
P47264
|
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: [Incanus, hasDebatedEtymology, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDebatedEtymology Context triple: [Incanus, hasDebatedEtymology, Yes]
-
A.
hasDebatedOrigin
Indicates that there is uncertainty or disagreement about the true origin or source of something.
-
B.
hasDebatedMeaning
chosen
Indicates that the meaning or interpretation of something is contested, disputed, or subject to ongoing debate.
-
C.
hasSourceOfDebate
Indicates that something is the origin or cause of an ongoing disagreement, controversy, or dispute between parties.
-
D.
debatedAs
Indicates that one entity is discussed or argued over in terms of being equivalent to, or serving in the role of, another entity within a debate or comparative argument.
-
E.
debatedBetween
Indicates a situation in which two or more parties engage in a discussion or argument over differing views about a particular issue or topic.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 1, 2026, 12:28 a.m.