Triple
T641580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tractatus Logico-Philosophicus |
E16749
|
entity |
| Predicate | hasSevenMainPropositions |
P17647
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tractatus Logico-Philosophicus, hasSevenMainPropositions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSevenMainPropositions Context triple: [Tractatus Logico-Philosophicus, hasSevenMainPropositions, true]
-
A.
hasMainProponent
Indicates that one entity is the primary advocate, champion, or leading supporter of another entity.
-
B.
hasProportion
Indicates that one entity stands in a specified ratio, fraction, or relative share to another entity or whole.
-
C.
hasMajorityOpinionBy
Indicates that a majority of the relevant group or decision-making body holds or supports the opinion expressed by the referenced entity.
-
D.
hasMainOrgan
Indicates that an entity possesses a primary or principal organ that plays a central role in its biological or functional system.
-
E.
hasMainRepresentative
Indicates that one entity serves as the primary or official representative of another entity.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f02bc2c8190b8a92b2505768c19 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0830008190a26ee158ed4dd1fe |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49df0de3c81909721eb391ec94031 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.