Triple
T6405106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Liberation |
E144158
|
entity |
| Predicate | hasCompanionsCountApprox |
P45948
|
FINISHED |
| Object | a few hundred recipients |
—
|
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 few hundred recipients | Statement: [Order of Liberation, hasCompanionsCountApprox, a few hundred recipients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionsCountApprox Context triple: [Order of Liberation, hasCompanionsCountApprox, a few hundred recipients]
-
A.
hasNumberOfCompanions
chosen
Indicates the quantity of companions or associates that an entity has.
-
B.
hasCompanionPiece
Indicates that one item is conceptually or functionally paired with another item as its companion piece.
-
C.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
D.
viewsCompanions
Indicates that an entity observes or looks at its companions or associates.
-
E.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c068b22c74819092228010708aec6b |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:35 p.m.