Triple
T19587994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovells |
E470152
|
entity |
| Predicate | lawyerCountBeforeMerger |
P56026
|
FINISHED |
| Object | over 1900 |
—
|
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: over 1900 | Statement: [Lovells, lawyerCountBeforeMerger, over 1900]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawyerCountBeforeMerger Context triple: [Lovells, lawyerCountBeforeMerger, over 1900]
-
A.
numberOfLawyers
chosen
Indicates the quantity of lawyers associated with a given entity or situation.
-
B.
governingBodyBeforeMerger
Indicates that one entity functioned as the governing body of another entity prior to a merger event.
-
C.
affiliationBeforeMerger
Indicates that an entity was affiliated with another entity prior to a merger event involving one or both of them.
-
D.
marketPositionBeforeMerger
Indicates the competitive or strategic position an entity held in the market prior to a specific merger taking place.
-
E.
mergerPartner
Indicates that two entities are involved as counterparties in a merger transaction with each other.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64052f61c81908bb49927d4246030 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.