Triple
T18968378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | difference principle |
E464100
|
entity |
| Predicate | orderedAfter |
P37518
|
FINISHED |
| Object | basic liberties principle |
—
|
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: basic liberties principle | Statement: [difference principle, orderedAfter, basic liberties principle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderedAfter Context triple: [difference principle, orderedAfter, basic liberties principle]
-
A.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
B.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
C.
orderOf
chosen
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
D.
joinedOrderOf
Indicates that an entity became a member of, or formally joined, a particular order or organization.
-
E.
orderedProtectionBy
Indicates that one entity has formally requested or arranged protective measures to be provided by another entity.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6172888819090a8b3cb1db20496 |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon