Triple
T15860720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTL* |
E384578
|
entity |
| Predicate | hasPathQuantifier |
P120795
|
FINISHED |
| Object | A |
—
|
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: A | Statement: [CTL*, hasPathQuantifier, A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPathQuantifier Context triple: [CTL*, hasPathQuantifier, A]
-
A.
usesQuantification
Indicates that one entity employs or applies a system of quantification (such as numerical or measurable assessment) to another entity or context.
-
B.
quantifiesOver
Indicates that one entity expresses a quantity, measurement, or numerical specification that applies to or ranges over another entity.
-
C.
hasQualifier
Indicates that one entity serves as a qualifier or modifier that further specifies or restricts the meaning or scope of another entity or statement.
-
D.
hasExpressionIn
Indicates that one entity is manifested, represented, or realized within another entity, typically as a specific form, version, or expression.
-
E.
hasExistentiale
Indicates that an entity possesses or is associated with an existential characteristic, condition, or mode of being.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:50 a.m.