Triple
T30892141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro Aris et Focis |
E786926
|
entity |
| Predicate | prepositionMeaning |
P63950
|
FINISHED |
| Object | pro = for, on behalf of |
—
|
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: pro = for, on behalf of | Statement: [Pro Aris et Focis, prepositionMeaning, pro = for, on behalf of]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prepositionMeaning Context triple: [Pro Aris et Focis, prepositionMeaning, pro = for, on behalf of]
-
A.
prepositionMeaningOfSine
Indicates that the preposition expresses the semantic meaning or sense of the word “sine.”
-
B.
meaningOfPhrase
Indicates that one entity expresses or defines the semantic content or interpretation of a given phrase.
-
C.
hasPrepositions
Indicates that one entity includes, uses, or is associated with one or more prepositions in relation to another entity.
-
D.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
E.
hasPreposition
chosen
Indicates that one entity is associated with or linked to another entity through a specific prepositional relationship.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6923826008190931f5076cd002373 |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:49 p.m.