Triple
T33687732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tangere |
E863086
|
entity |
| Predicate | transitivity |
P157343
|
FINISHED |
| Object | transitive verb |
—
|
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: transitive verb | Statement: [Tangere, transitivity, transitive verb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitivity Context triple: [Tangere, transitivity, transitive verb]
-
A.
edgeTransitivity
chosen
Indicates how consistently connections between entities form transitive patterns, such that if one entity is linked to a second and the second to a third, there is also a direct link between the first and third.
-
B.
isSimplyTransitiveUnder
Indicates that one entity acts on another in a way that is transitive and free, so each target is reached by exactly one action of the first entity.
-
C.
transition
Indicates a change of state or condition from one form, phase, or situation to another.
-
D.
transcendenceRelation
Indicates a relationship in which one entity surpasses, goes beyond, or exists at a higher or more encompassing level than another.
-
E.
arity
Indicates the number of arguments or participants that a relation or function takes.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 1, 2026, 1:43 a.m.