Triple
T2972010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Searching Authority |
E80300
|
entity |
| Predicate | selectionDependsOn |
P24478
|
FINISHED |
| Object | receiving Office |
—
|
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: receiving Office | Statement: [International Searching Authority, selectionDependsOn, receiving Office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionDependsOn Context triple: [International Searching Authority, selectionDependsOn, receiving Office]
-
A.
selectionOrderInfluencedBy
chosen
Indicates that the order in which items are selected is affected or determined by another factor, condition, or entity.
-
B.
roleDependsOn
Indicates that the existence, behavior, or permissions of one role are contingent upon or derived from another role.
-
C.
selectionMadeBy
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
D.
observerDependent
Indicates that the truth, value, or manifestation of something varies depending on which observer is considering or measuring it.
-
E.
selectionFrom
Indicates that one entity is chosen as a member or subset from a larger set or collection represented 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad998656948190ba79d7196d735f34 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.